Skip to content

Support configuration cache - #74

Merged
osipxd merged 1 commit into
developfrom
feature/configuration-cache
Nov 11, 2026
Merged

osipxd merged 1 commit into
developfrom
feature/configuration-cache

Conversation

@osipxd

@osipxd osipxd commented Nov 11, 2026

Copy link
Copy Markdown
Member

Makes BukkitGradle compatible with the configuration cache and declares it on the Plugin Portal.

Changes

  • Breaking: remove the :parsePluginYaml task.
    It set conventions on the bukkit.plugin model during execution, which fails with the configuration cache: the task gets a deserialized copy of the model, and changes never reach :mainResourceFactory.
    The source plugin.yml is now parsed while :mainResourceFactory is configured, using providers.fileContents, so the configuration cache is invalidated when the file changes.
    The file is decoded as UTF-8 regardless of the default charset.
  • Update com.gradle.plugin-publish 1.3.1 → 2.2.1 and declare configurationCache = true.
  • Tests run with --configuration-cache, with new tests for cache reuse and for regeneration after the source plugin.yml changes or is created.

Verification

  • ./gradlew check passes (64 tests).
  • ./gradlew publishPlugins --validate-only passes without the compatibility warning.
  • Sample project with a source plugin.yml: jar and runServer --dry-run store and reuse the configuration cache, and the jar contains the merged plugin.yml.

Checklist:

  • Have you read text of project license?
  • Have you described maked changes in README or wiki?
  • Have you added changelog?

🤖 Generated with Claude Code

@osipxd
osipxd merged commit a01d61c into develop Nov 11, 2026
2 checks passed
@osipxd
osipxd deleted the feature/configuration-cache branch November 11, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant